Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid loading and parsing unconfigured non-inline modules. #36482

Merged

Conversation

jseyfried
Copy link
Contributor

@jseyfried jseyfried commented Sep 14, 2016

For example, #[cfg(any())] mod foo; will always compile after this PR, even if foo.rs and foo/mod.rs do not exist or do not contain valid Rust.

Fixes #36478 and fixes #27873.

r? @nrc

@jseyfried
Copy link
Contributor Author

cc @durka @retep998 @eddyb

@jseyfried jseyfried force-pushed the dont_load_unconfigured_noninline_modules branch from f18f0e3 to 6f0ee45 Compare September 15, 2016 08:17
@nrc
Copy link
Member

nrc commented Sep 16, 2016

@bors: r+

@bors
Copy link
Contributor

bors commented Sep 16, 2016

📌 Commit 6f0ee45 has been approved by nrc

@sfackler sfackler added the relnotes Marks issues that should be documented in the release notes of the next release. label Sep 16, 2016
@bors
Copy link
Contributor

bors commented Sep 17, 2016

⌛ Testing commit 6f0ee45 with merge 141012d...

bors added a commit that referenced this pull request Sep 17, 2016
…ules, r=nrc

Avoid loading and parsing unconfigured non-inline modules.

For example, `#[cfg(any())] mod foo;` will always compile after this PR, even if `foo.rs` and `foo/mod.rs` do not exist or do not contain valid Rust.

Fixes #36478 and fixes #27873.

r? @nrc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
relnotes Marks issues that should be documented in the release notes of the next release.
Projects
None yet
4 participants